Skip to content

docs: stop naming the upstream conduit, and stop pricing against it - #74

Merged
VickyXAI merged 2 commits into
mainfrom
docs/no-upstream-disclosure
Sep 3, 2026
Merged

docs: stop naming the upstream conduit, and stop pricing against it#74
VickyXAI merged 2 commits into
mainfrom
docs/no-upstream-disclosure

Conversation

@VickyXAI

@VickyXAI VickyXAI commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Vicky, 2026-09-03: 「我们现在官网还说我们的背后就是 openrouter 这个要改啊」. Two separate leaks, both public.

1. Routing disclosure (docs/resources/changelog.md)

The changelog named the wholesale conduit four times:

Line What it said
30 two free models "serve from OpenRouter's $0 pool"
14 "the OpenRouter route is unavailable under our account's data policy" — the conduit and our account state
187 grok-4.5 "verified on both the direct-xAI and OpenRouter routes"
190 the long-context tier attributed to "xAI (and OpenRouter)"

This is the same leak class src/lib/models-description-leak.test.ts already pins for model description fields, just written in prose instead of data.

Every measurement survives. The free-tier entry keeps 4.9s against 16.3s and the 1M-token context; it now says the models moved to a larger free-tier pool with their previous route as the fallback — the part a caller can actually act on.

2. Price parity

we match OpenRouter / no margin, matches OpenRouter appeared on the pricing sheet, the intelligence overview and the models API reference. It reads as "OpenRouter is what is behind us."

The claim carrying the weight is 0% platform margin on chat tokens, and each of those sentences already states it in full — the competitor's name was doing no work, so it is deleted rather than reworded.

Not touched

Comparison pages. Naming OpenRouter as a competitor is deliberate positioning, not a routing disclosure — the same distinction models-description-leak.test.ts draws.

After this, grep -ri openrouter docs/ returns nothing outside ClawRouter.

1bcMax added 2 commits September 3, 2026 16:05
Two separate leaks, both public.

Routing disclosure. The changelog named the wholesale conduit four times:
two free models "serve from OpenRouter's $0 pool"; the DeepSeek vision
entry volunteered that "the OpenRouter route is unavailable under our
account's data policy" (the conduit AND our account state); grok-4.5 was
"verified on both the direct-xAI and OpenRouter routes"; and the
long-context tier was attributed to "xAI (and OpenRouter)". None of that
is ours to publish — it is the same class src/lib/models-description-leak.test.ts
pins for model descriptions, just written in prose instead.

Every measurement survives. The free-tier entry keeps 4.9s against
16.3s and the 1M-token context; it now says the models moved to a larger
free-tier pool with their previous route as the fallback, which is the
part a caller can act on.

Price parity. "we match OpenRouter" / "no margin, matches OpenRouter"
appeared on the pricing sheet, the intelligence overview and the models
API reference. It reads as "OpenRouter is what is behind us". The claim
that carries the weight is 0% platform margin on chat tokens, and each
of those sentences already states it — the competitor's name was doing
no work, so it is gone rather than reworded.

Comparison pages are untouched: naming OpenRouter as a competitor is
deliberate positioning, not a routing disclosure.
Found by the prose guard added alongside this change (blockrun
src/lib/upstream-disclosure-prose.test.ts), not by grepping — the sweep
derives its forbidden words from CONDUIT_PROVIDERS, which is openrouter
AND token360, and every hand-written pass had only looked for the first.

"Token360 charges nothing for asset storage" names the white-label
upstream behind portrait enrolment, which displayProvider() exists to
rewrite to bytedance everywhere else. The price history and the reason
for the cut are unchanged.
@VickyXAI
VickyXAI merged commit cacc215 into main Sep 3, 2026
@VickyXAI
VickyXAI deleted the docs/no-upstream-disclosure branch September 3, 2026 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant